home *** CD-ROM | disk | FTP | other *** search
/ Columbia Kermit / kermit.zip / newsgroups / misc.19970929-19971216 / 000169_news@newsmaster….columbia.edu _Wed Oct 22 19:10:22 1997.msg < prev    next >
Internet Message Format  |  2020-01-01  |  3KB
  1. Return-Path: <news@newsmaster.cc.columbia.edu>
  2. Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
  3.     by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id TAA26391
  4.     for <kermit.misc@watsun.cc.columbia.edu>; Wed, 22 Oct 1997 19:10:21 -0400 (EDT)
  5. Received: (from news@localhost)
  6.     by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id TAA15569
  7.     for kermit.misc@watsun; Wed, 22 Oct 1997 19:10:21 -0400 (EDT)
  8. Path: news.columbia.edu!panix!howland.erols.net!news.mathworks.com!mvb.saic.com!news.eskimo.com!jimo
  9. From: jimo@eskimo.com (Jim Osborn)
  10. Newsgroups: comp.protocols.kermit.misc
  11. Subject: Re: login script beeps unexpectedly
  12. Date: 22 Oct 1997 23:03:47 GMT
  13. Organization: Eskimo North (206) For-Ever
  14. Lines: 44
  15. Message-ID: <62m0oj$a7h$1@eskinews.eskimo.com>
  16. References: <62ejvl$fpk$1@eskinews.eskimo.com> <62ft4g$j94$1@apakabar.cc.columbia.edu> <62h9lb$pbm$1@eskinews.eskimo.com> <62icqn$582$1@apakabar.cc.columbia.edu>
  17. NNTP-Posting-Host: eskimo.com
  18. Xref: news.columbia.edu comp.protocols.kermit.misc:7949
  19.  
  20. In article <62icqn$582$1@apakabar.cc.columbia.edu>,
  21. Frank da Cruz <fdc@watsun.cc.columbia.edu> wrote:
  22. >OK, let's look at your script more closely:
  23. >
  24. >: >: define eskimo {
  25. >: >:     while not defined \%1 {
  26. >: >:         askq \%1 {Eskimo Password: }
  27. >: >:     }
  28. >: >:     :retry
  29. >: >:     dial 258-0759
  30. >
  31. >You need an IF FAIL statement here.  You don't want the script to keep
  32. >executing if your DIAL command fails.
  33.  
  34. Agreed; I want it to start over, and it would be cleaner to tell it
  35. that explicitly.
  36.  
  37. >...
  38. >Ditto.  In fact, if this one fails, you can fall through the next test
  39. >and then (since the subsequent INPUTs are also untested), out comes the beep.
  40. >
  41. >: >:     xif \find({CLI,,27},\v(input)) {  #Start over if toxic modem
  42. >: >:         xif \find({@seattle2},\v(input)) {
  43. >: >:             echo {Aborting 27,,2}
  44. >: >:             goto retry
  45. >: >:         }
  46. >: >:     }
  47. >: >:...
  48.  
  49. This is all true, but doesn't address the situation where I watched the
  50. action pass by on my screen, seeing the toxic modem sucessfully
  51. detected, the abort message sucessfully echoed, the beep sounded,
  52. and the dialing process restarted, again and again.
  53.  
  54. I will clean up those unchecked failure possibilities, but I think
  55. the mystery beep must come from elsewhere.  Unfortunately (or is
  56. it really fortunately?:) I don't get offered that awful modem often
  57. enough to test the script at will.  I'll try relaxing the xif
  58. conditions to something more frequent and let you know how the
  59. cleanup influences things.
  60.  
  61. Thanks again,
  62.  
  63. Jim